I do not really think we need specific variations of AsyncResource (sync init + async shutdown, async init + sync shutdown) because the way how async stuff works in Python. async def function that never awaits have performance of the regular generator (see docs on coroutines), since it never switches to the event loop.

Our Resource providers are context-manager-aware now (since next release), so something-like this is now possible:

class Container(containers.DeclarativeContainer):
    my_http_client = providers.Resource(aiohttp.ClientSession, base_url="http://example.com/foo/")

Workarounds like proposed AsyncShutdownResource are no longer needed, so closing this PR.